Content Stylesheet Change Log
SPRINT 905/02/2017 - 05/16/2017
| URLA Dynamic Authoring New Stylesheet |
|---|
|
| Summary: This stylesheet will be exactly like the WKFS_StyleGuide_IntegratedDisclosures but we will be using the tagline out of the WKFS_StyleGuide. |
| Technical Notes: None |
| Implementation Notes: This feature requires a Content Style Sheets update. |
Revision 2016.2 04/16/2016 - 08/04/2016.
| Remove Duplicate Imports From Stylesheets To Support Java 8 & Saxon Upgrade |
|---|
|
| Issue: Using Java 8 resulted in failed PDFs due to duplicate imports in content stylesheets. |
Solution: A script was created and executed against the Content Stylesheets which removes imports that have already been imported on a ‘parent’ stylesheet. The following stylesheets were updated with this script process:
|
| Implementation Notes: This feature requires a Content Style Sheet update. |
Enhancements
The effective date for all products within the scope of this document for this release is 11/05/2015 - 04/15/2016.
| TagTree Structure Minimization |
|---|
|
| Summary: Modified creation of the TagTree structure to simplify the tags and meet proper tagging requirements as follows: consolidated separate paragraph tags to eliminate the extra ‘pause’ by screen readers, removed tags with empty values, replaced incorrectly used paragraph and span tags with either sections or divisions. |
| Technical Notes: Modified FOPRender.java to add support for FillableCheckbox to FoFIlter. Added ID attribute to Signer object created by FOAcroFormFieldFilter. Added ADA roles to various components in layout tables; remove tags for non-breaking spaces. Rewrite logic that cleans up the tag tree before final PDF production. Modified Content Stylesheets to add role attribute for Sections; fix missing fo:table-row in Signature markup; add role attribute to Para and FragmentedPara. |
| Implementation Notes: This feature requires an Expere Engine Update and Content Stylesheets update (Stylesheets Modified: WKFS_StyleGuide.xsl, Signature.xsl, Sections.xsl). |
| Tagline Separator Line | ||||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
| Summary: The TaglineSeparatorLine attribute has been added to the Document element, providing the ability to suppress printing the Tagline separator line. | ||||||||
Technical Notes:
|
||||||||
| Implementation Notes: This feature requires a Content Stylesheet and a Requirements Editor Tool update. |
Defects
| Spaces no longer trimmed when authored in phrase |
|---|
|
| Issue: Resolved an issue identified with FragmentedPara’s where the Phrase element had spaces authored which were getting removed when the PDF was rendered. |
| Solution: Modified WKFS_StyleGuide.xls to remove the fo:Inline wrapper added to otherwise clause. |
| Implementation Notes: This feature requires a Content Style Sheet update. |
| eInitials printing incorrect line widths |
|---|
|
| Issue: When generating documents that include eInitials, the line width is printing 2.5 inch, which is the length for the eSignature field. Previously, when the Esignature type 'initials' was chosen, the line coming from the signature element still printed full width. |
| Solution: Now, when Esignature elements are present and the type 'initials' is chosen and the Length attribute is not authored, the signature line is the same width as the Esignature initial box by default, not standard full width. If Length attribute is authored, that attribute is honored. |
| Implementation Notes: This feature requires a Requirements Editor Tool update. |
| Ancillary Barcode printing over tagline resolved |
|---|
|
| Issue: Users reported that the ancillary barcode printed over the document tagline on certain documents from the October content release. Note: No issues existed with TRID or static documents.
|
| Solution: There was a change made to the WKFS_StyleGuide. Now the barcodes will no longer render over the top of a footer or tagline. |
| Implementation Notes: his feature requires a content stylesheet update which will be available in the November content. |
| Alignment 'Justify' not working correctly for Notice Element |
|---|
|
| Issue: An issue was identified with the alignment attributes (Justify, LEft, Right, Center) of the Notice/NoticeContent element in that when there is a bold, italic, all caps, small caps, small font, large font, or title font emphases wrapped around the content, the information would not print as selected. |
| Solution: The Content stylesheet was modified to correct the issue. Now, if emphases are wrapped around the content, the information prints as expected. |
| Implementation Notes: This feature requires a style sheet (WKFS_StyleGuide.xsl) update. |